Make jnosql-tinkerpop work with ArangoDB and TinkerGraph #337
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
This PR adds to
jnosql-tinkerpoptests for ArangoDB and TinkerGraph backends.The same tests are now run against the following matrix of graph providers:
This can be in future further extended with additional tinkerpop graph providers.
In addition, to make this work, the following changes have been made to
jnosql-tinkerpopproduction code:~id), seeorg.apache.tinkerpop.gremlin.structure.T#id.nullid throws nowIllegalArgumentExceptioninstead ofEmptyResultException.DefaultTinkerpopGraphDatabaseManager#insert(CommunicationEntity)has been optimized persisting id, label and properties atomically.The following changes have been made to
jnosql-tinkerpoptest code:String@Id("~id")